Application Insights (1 / 36): You're debugging a performance issue in a multi-service architecture. Application Map shows incomplete dependency lines between services.
What are the likely causes?
Answer:
The likely causes for incomplete dependency lines between services in a multi-service architecture, as indicated by the Application Map, are:
- Services send telemetry to separate Application Insights resources. This breaks the map since Application Insights doesn’t correlate across resources.
cloud_RoleName is not uniquely configured per service. This prevents unique nodes from appearing in the Application Map.
Other options are less likely or irrelevant:
- The
service.namespace being missing from some components could cause grouping issues but not necessarily map breakage.
- Services not exposing their metrics via Prometheus exporters is irrelevant to Application Insights.
- HTTP calls between services being done using raw TCP sockets is a problem because Application Map expects HTTP dependencies, but this is not one of the primary causes listed.